From: Allen Wirfs-Brock [Allen.Wirfs-Brock@microsoft.com] Sent: jeudi 4 novembre 2010 02:24 To: Istvan Sebestyen; Patrick Charollais; Neumann, J. Subject: Final editor's draft for ISO 16262 ed3 BRM Attachments: IS-16262 editors draft with markup.zip The attached zip file contains what should be my final drafts of the ISO version of the ECMAScript specification for the BRM. There are three files: “editors comment disp nov.doc” is the filled in Editor’s comments disposition document. “IS-16262 editors draft with markup.doc” is the specification with all change markup present and visible “IS-16262 editors draft clean.doc” is the same specification with all changes “accepted” and comments removed Patrick, there are a couple items that you probably need to attend to before posting these documents: I did not attempt to update any of the ISO document/date nomenclature on the title page or headers/footers. Given that the BRM has slipped into 2011 I assume that some of these should change accordingly but I’ll leave that to you. Also, in response to one of the comments I added several items to the Bibliography at the end of the document, primarily RFC references. Since I didn’t have immediate access to the ISO document on bibliographic entries I winged it based upon other ISO documents I could see. You may want to check the new entries against ISO expectations. Finally, In the course of processing the comments I also located a number of additional editorial errors. I corrected and marked each such change with a markup comment. Also, at the end of the disposition document added a paragraph listing the sections containing such changes. It this is too out of line, we can reject all those changes. However, in seemed silly to simply ignore obvious errors. Finally, if you make any edits for any of the above, it will probably be easiest to make them separately in both the markup and clean version of the document. There are two changes in 11.13 and A.3 that requires a manual operation (other than “accept all”) to make the clean version from the markup version. This is noted in a markup comment in those sections but if your edits are small it is probably easiest to make them separately in each copy and not completely go through regeneration of the clean version from the markup version. Let me know if you have any questions or see any additional problems. Allen